We have been transitioning to the new coding style for a while now,
and there has been reasonable progress. So hopefully it is not too
intrusive at this point to enforce non-legacy style for all lines
that are changed in a merge request. If it turns out to be still too
annoying, we can always reconsider and turn off the additional job.
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1497
BUNDLE: "extensions-git.flatpak"
JS_LOG: "js-report.txt"
LINT_LOG: "eslint-report.xml"
+ LINT_MR_LOG: "eslint-mr-report.xml"
.only_default: &only_default
only:
junit: ${LINT_LOG}
when: always
+eslint_mr:
+ image: registry.gitlab.gnome.org/gnome/gnome-shell/extension-ci:v2
+ stage: review
+ script:
+ - export NODE_PATH=$(npm root -g)
+ - ./.gitlab-ci/run-eslint --output-file ${LINT_MR_LOG} --format junit
+ --remote ${CI_MERGE_REQUEST_PROJECT_URL}.git
+ --branch ${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}
+ only:
+ - merge_requests
+ artifacts:
+ reports:
+ junit: ${LINT_MR_LOG}
+ when: always
+
potfile_check:
image: registry.gitlab.gnome.org/gnome/gnome-shell/extension-ci:v2
stage: review